feat(scaffold): reroute materializer to @stackbilt/scaffold-core#53
Merged
Conversation
Replaces direct `materializeScaffold` calls in gateway.ts and
rest-scaffold.ts with `buildScaffold` from @stackbilt/scaffold-core.
Because charter#220 (publish) is still open, a shim at
scaffold-core-shim.ts bridges the gap: it wraps the existing
scaffold-materializer.ts behind the LocalScaffoldResult API contract
(files with { path, content, role }, plus nextSteps). Both call sites
strip the `role` field when forwarding files to downstream consumers.
When charter#220 merges:
1. `npm install` picks up @stackbilt/scaffold-core
2. Uncomment the direct import in gateway.ts and rest-scaffold.ts
3. Delete scaffold-core-shim.ts and scaffold-materializer.ts
TODO comments reference charter#220 in both changed files.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…caffold-core@1.0.0 Removes the local scaffold-core-shim.ts and scaffold-materializer.ts; gateway.ts and rest-scaffold.ts now import directly from the published npm package. Removed the non-existent `nextSteps` field references (LocalScaffoldResult has no such field — fallback generation handles next steps downstream). Typecheck clean, 183/183 tests green. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…minates TarotScript 401 scaffold_classify was calling TarotScript /run (classify-cast spread) without auth, causing HTTP 401. Now calls classify() from @stackbilt/scaffold-core directly: zero network, zero inference, <1ms. Returns pattern/confidence/traits/qualityProfile. Updated gateway test to verify output shape instead of header pass-through. Closes #51 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
materializeScaffoldcalls ingateway.tsandrest-scaffold.tswithbuildScaffoldfrom@stackbilt/scaffold-core@stackbilt/scaffold-core: ^1.0.0topackage.jsonscaffold-core-shim.tsas a temporary bridge (wraps the existing local materializer behind theLocalScaffoldResultAPI contract) until charter#220 publishes the packagebuildScaffoldreturnsScaffoldFile[]with{ path, content, role }— both call sites striprolewhen forwarding files to consumersscaffold-materializer.tsis retained for now (shim depends on it); delete it along with the shim once the package is liveActivation path once charter#220 merges
npm installpicks up@stackbilt/scaffold-coreimport { buildScaffold } from '@stackbilt/scaffold-core'lines ingateway.tsandrest-scaffold.tssrc/scaffold-core-shim.tsandsrc/scaffold-materializer.tsTest plan
npm run typecheck— cleannpm test— 183/183 passingnpm install --dry-runconfirms 404 on unpublished package (expected; shim path handles it)Closes #50
🤖 Generated with Claude Code